home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
dev
/
www_talk.930
/
001198_weber@eitech.com _Thu May 27 18:13:45 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-01-24
|
2KB
Return-Path: <weber@eitech.com>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA21057; Thu, 27 May 93 18:13:45 MET DST
Received: from lks.lks.csi.com by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
id AA13102; Thu, 27 May 1993 18:35:09 +0200
Received: from eitech.eitech.com by lks.lks.csi.com (5.65/6.930123)
with SMTP id AA24029; Thu, 27 May 93 11:34:08 -0500
Received: from bd.eitech.com ([192.100.58.27]) by eitech.com (4.1/SMI-4.1)
id AA23627; Thu, 27 May 93 09:29:57 PDT
Message-Id: <9305271629.AA23627@eitech.com>
X-Sender: weber@eitech
Date: Thu, 27 May 1993 09:35:44 -0800
To: murphy@dccs.upenn.edu, www-talk@nxoc01.cern.ch
From: weber@eitech.com (Jay Weber)
Subject: Re: Keeping HTML Simple & Format negotiation between Browser & Server
Cc: litwack@dccs.upenn.edu
X-Mailer: <PC Eudora Version 1.1a5>
At 09:46 AM 5/27/93 -0400, murphy@dccs.upenn.edu wrote:
>Elements needed:
>
>1) an ever-growing dictionary of pre-defined format names and
>agreement on what those format names mean. It has to be ever-growing
>because it's a fact of life -- there's always going to be new types of
>data formats coming onto the scene. The server and the browser
>(client) both need access to this dictionary, perhaps getting a new
>version of it every once in a while (either automatically, or perhaps
>upon the user's request)
That's easy, MIME types are registered with the Internet Naming Authority,
IANA.
>2) The document format (HTML, HMML, whatever) needs to accomodate
>documents which have multiple items in it, which could be different
>types, such as an embedded graph and a mathematical formula. AND each
>of the items themselves COULD be expressed in a number of different
>format types.
I'll wave the MIME flag again and point out that MIME has a modular
bundling mechanism -- the embedded object can be of type multipart/mixed.
> The information which the two alternatives convey would
>not have to be exactly equivalent -- sometimes a picture is worth a
>thousand words! But if text is all your device can display, you might
>settle for the words. The person who maintains the document can put
>both text & image in the document, and the image would be displayed if
>possible.
MIME again! The MIME type multipart/alternative allows you to specify
a series of alternative objects, ordered by preference.
More HTML enthusiasts should check out MIME.
Jay Weber
EIT